Why?
Did aws-c-common break ABI with the latest update?

Yes.
URI related codes were moved to aws-c-common from aws-c-io:

• awslabs/aws-c-common@be12242
• awslabs/aws-c-io@550e319

package-grokker (https://github.com/msys2/MINGW-packages/actions/runs/3255290437/jobs/5344618607#step:3:64) showed:

mingw-w64-aws-c-http
mingw-w64-aws-c-mqtt
mingw-w64-aws-c-s3
mingw-w64-aws-c-auth
mingw-w64-aws-crt-cpp

I'm sorry but I don't know how to interpret the result...
Could you explain it?

Does it show that these packages don't need to be rebuilt?

I'm sorry but I don't know how to interpret the result...
Could you explain it?

It shows the packages that should have been rebuilt due to ABI breaks.

Though it's unusual for a package to require rebuilds for a patch update.

Ah, thanks. I understand. Then we may need to rebuild mingw-w64-aws-c-http and mingw-w64-aws-c-mqtt too. But they don't have any problem on my environment. They may not use removed APIs.

AWS SDK don't use semantic versioning. So we can't infer ABI compatibility from version number.

ok, thanks. I triggered a rebuild anyway, just to be safe.